Trac is being migrated to new services! Issues can be found in our new YouTrack instance and WIKI pages can be found on our website.

Changes between Version 124 and Version 125 of Protocol Specific Questions


Ignore:
Timestamp:
Sep 10, 2012, 4:28:27 AM (11 years ago)
Author:
datallah
Comment:

Fix wiki syntax issues with Trac 1.0

Legend:

Unmodified
Added
Removed
Modified
  • Protocol Specific Questions

    v124 v125  
    119119
    120120==== How do I change my resource string? ====
    121 Go to Accounts->Add/Edit.  Find your XMPP account and uncheck the Enabled box.  Select the account and click Modify.  Change the string in the Resource field.
     121Go to Accounts->!Add/Edit.  Find your XMPP account and uncheck the Enabled box.  Select the account and click Modify.  Change the string in the Resource field.
    122122
    123123==== How can I configure resource priority? ====
     
    130130  ||Extended Away||0||
    131131
    132 ==== Why can't I log on to my Google Talk/Google Apps account anymore? ==== #gtalk_srv
     132==== Why can't I log on to my Google !Talk/Google Apps account anymore? ==== #gtalk_srv
    133133In previous versions, Pidgin would automatically use the server `talk.google.com` to connect to your account. This was removed in version 2.5.2 so that these connections would not cause certificate errors.
    134134
     
    173173==== Why do I get an "SSL Handshake Failed" error when connecting to Oracle's XMPP server? ====
    174174
    175 The SSL/TLS implementation used by Oracle's XMPP server does not support TLS 1.0 or newer, and immediately aborts the negotiation if the ClientHello record version is newer than SSL 3.0.  This causes issues when Pidgin is built with GnuTLS SSL support, as GnuTLS defaults to negotiating TLS 1.0.  In order to work around this, you either need to build Pidgin with NSS SSL support or upgrade to Pidgin 2.7.0 or newer and run Pidgin like this:
     175The SSL/TLS implementation used by Oracle's XMPP server does not support TLS 1.0 or newer, and immediately aborts the negotiation if the !ClientHello record version is newer than SSL 3.0.  This causes issues when Pidgin is built with GnuTLS SSL support, as GnuTLS defaults to negotiating TLS 1.0.  In order to work around this, you either need to build Pidgin with NSS SSL support or upgrade to Pidgin 2.7.0 or newer and run Pidgin like this:
    176176
    177177{{{
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!